← All case studies
CS-011 · Financial Services · Synthetic Simulation

Savings Habit Decay & AutoPay Churn

Why income predicted almost nothing — and what actually did.

Personas 8
Shock events 4
Conversations 32
Best delta +41 pts
Overview

Eight micro-savers. Four shocks. One counterintuitive finding.

Eight synthetic personas spanning ₹9,500 to ₹48,000 monthly income were exposed to four shock events designed to stress-test AutoPay retention across a realistic range of financial and social triggers. The lowest-income persona — a domestic worker on ₹12,000/mo — was the most churn-resistant. The highest-income persona — an IT manager on ₹48,000/mo — churned on day 67 after a ₹505 paper loss.

The difference was not financial capacity. It was the nature of the saving identity each persona had built. Meena Kumari, the ASHA worker on ₹9,500/mo, saved through a 52-day stipend delay by borrowing from a self-help group to maintain her deposit. Vikram Nair, earning five times more, disengaged the moment his performance identity was disrupted.

The study found six of eight churns were friction-driven, not intentional. Mandate expiry (S3) produced the widest single-shock impact — churn risk of 4/10 or higher for six of eight personas — most of whom had no intention to stop saving. The primary product failure was not in motivation. It was in the renewal flow.

Key Metrics
8
Personas
4
Shock events
32
Conversations
+41
pts · Best delta
Key Findings
  • Mandate expiry (S3) produced churn risk ≥4/10 for 6 of 8 personas — the widest single-shock impact
  • Income was the primary churn predictor for 0 of 8 personas
  • 6 of 8 churns were friction-driven, not intentional — users wanted to continue
  • Flexible Pause (I5) was the only intervention with zero backfire cases across all segments
  • 3 interventions actively accelerated churn for specific persona types
Participants

Eight personas. ₹9,500 to ₹48,000/mo. Widely different retention profiles.

Simulation Transcripts

Four shock events. Eight personas. What actually drives AutoPay churn.

Recommendations

Four interventions. Ranked by evidence strength.

Immediate
Deploy Flexible Pause as a proactive default
Flexible Pause (I5) was the only intervention with zero backfire cases across all eight persona types. For friction-driven churners — Sunita, Dinesh, Meena — it reduced churn risk by an average of 5.2 points. It works because it preserves the saving identity while removing the compliance barrier.
Target segments: All — no persona type was harmed by its presence
Immediate
Instrument friction-churn vs. intent-churn separately
Six of eight churns in this study were friction-driven — the user intended to continue but could not complete the renewal or recovery flow. These are currently indistinguishable from intentional churn in server-side data. Separate instrumentation unlocks dramatically different intervention logic for each type.
Target segments: All — affects product analytics architecture, not user-facing
Short-term
Build persona-level intervention routing
Three interventions — Gamification (I4), Social Proof (I3) — actively accelerated churn for specific persona types (Pradeep, Vikram). The same message that retains a streak-driven saver (Arjun) damages trust for a SEBI-literate optimizer (Pradeep). Segment-level routing is necessary before any retention campaign can avoid net harm.
High-risk: Pradeep-type (accountants, financially literate); Vikram-type (performance-identity savers)
Short-term
Front-load identity-anchoring at onboarding
The highest-leverage finding in the study: Vikram Nair's Day 67 churn was architecturally predicted by his Day 1 onboarding. He had no named goal, no specific savings horizon, and no non-performance reason to save. Named goals at onboarding — a 10-second step — would have changed the entire behavioural architecture that led to churn.
Target segments: Performance-identity savers (Vikram-type); applies broadly at onboarding
Open Questions

What this study cannot answer.

Run your own simulation.

Simulatte builds synthetic micro-savers, trust-network-dependent users, and performance-identity customers for any financial product — then stress-tests retention logic before you build it into production.